home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-11
/
vs_804.zip
/
VERNSIX.DOC
< prev
next >
Wrap
Text File
|
1991-10-13
|
13KB
|
533 lines
Vern Six's Clipper ToolBox
for Clipper v5.0x
*********************************
*** SHAREWARE EVALUATION COPY ***
*********************************
October 13, 1991
Release 8.00
Copyright (c) 1991 by Vernon E. Six, Jr.
All Rights Reserved World Wide
VERNSIX5.LIB is distributed through:
FrontLine Software
2908 Forest Hollow Lane, #2329
Arlington, Texas 76006
Ph: 214/283-3282 - Voice
Ph: 817/695-0058 - BBS
Vernon E. Six, Jr. may be contacted electronically via:
CompuServe: 72240,3122
FidoNet: 1:124/4003.0
ClipMail: CLIPBRD_HOME
1
Table of contents
-----------------
Licensing Terms and Conditions . . . . . . . . . . . . . . . 3
Disclaimer of Warranty . . . . . . . . . . . . . . . . . . . 5
How my programs are assigned version numbers . . . . . . . . 6
Syntax Conventions . . . . . . . . . . . . . . . . . . . . . 9
Variable naming conventions . . . . . . . . . . . . . . . . . 9
2
Licensing Terms and Conditions
------------------------------
Copyright (c) 1988-91 by Vernon E. Six, Jr.
All Rights Reserved World Wide.
VernSix5.Lib may only be used and distributed under the
following conditions:
1) You may use VernSix5.Lib for a period of up to thirty
days to determine its suitability for your needs. If
you continue to use VernSix5.Lib (or any program with
VernSix5.Lib linked into it) after a period of thirty
days you MUST register your copy.
A registration form is included in the distribution
files with the name of REGISTER.FRM.
2) When you register your copy of VernSix5.Lib, you will
receive:
a) the latest version without the "advertisemnet"
screen
b) a royalty free run-time license to use
VernSix5.Lib in any of your applications.
c) complete source code
3) You may distribute VernSix5.Lib provided that no fee is
charged, except for a nominal "diskette" fee or
"connect time" charges. In any event, the entire fee
shall not exceed $10.00. This does NOT apply to
commercial packages developed using VernSix5.Lib (see
paragraphs 1 and 2).
4) You may NOT use VernSix5.Lib in conjunction with any
commercial endeavor without
a) registering your copy, and
b) seriously considering providing a "blurb" line
about theauthor of VernSix5.Lib i.e. "This
application uses VernSix5.Lib. Copyright (c) 1991
by Vernon E. Six, Jr." somewhere in your
application's documentation.
5) You may NOT distribute VernSix5.Lib in modified form.
6) If you distribute VernSix5.Lib, it MUST be in the
3
original "archive" as released by the author. You may
not add any files, archive comments, nor may you
re-archive it using some other archive program, etc.
This is to ensure that my software hasn't been tampered
with.
4
Disclaimer of Warranty
----------------------
*** NO WARRANTY ***
Because VernSix5.Lib is distributed as "SHAREWARE", I provide
absolutely no warranty, to the extent permitted by applicable
state law.
Except when otherwise stated in writing, Vernon E. Six, Jr.,
FrontLine Software and/or other parties provide VernSix5.Lib "AS
IS" without warranty of any kind, either expressed or implied,
including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. The entire
risk as to the quality and performance of VernSix5.Lib is with
you. Should VernSix5.Lib prove defective, you assume the cost of
all necessary remedies, repair or correction.
In no event will Vernon E. Six, Jr. and/or FrontLine Software be
responsible in any way for the behavior of modified versions of
VernSix5.Lib. In no event, unless required by applicable state
law, will Vernon E. Six, Jr., FrontLine Software or any other
party who may distribute VernSix5.Lib as permitted in the
licensing agreement, be liable to you for damages, including any
lost profits, lost monies, or other special, incidental or
consequental damages arising out of the use or inability to use
(including but not limited to loss of data or data being render
inaccurate or losses sustained by third parties or a failure of
the program to operate with any other program) VernSix5.Lib, even
if you have been advised of the possibility of such damages, or
any claim by any other party.
5
How my programs are assigned version numbers
--------------------------------------------
With any programming effort there are several phases of
development. The phases that my products go through are listed
below.
Phase 1) Planning & Design
This is where the product is completely laid out. i.e.
Exactly what do we want to accomplish with this product?
What are the major steps necessary to accomplish this? Data
normalization, etc.
Phase 2) Detail definition
During this phase I break the total product into several
much smaller pieces. i.e. What are the database
structures? What will the screens look like? etc.
Phase 3) Program Development
This is phase where I try to put several of the smaller
pieces together. This is also known as the "Alpha" stage of
the product. Several test releases of the product will be
made during this time. These releases are called "Alpha
releases".
An "Alpha" release signifies that new development on the
product has taken place. i.e. new functions & features
have been added since the last "Alpha" release.
Phase 4) Debugging & Final Polishing
This phase begins when all the smaller pieces are in place
and all "Alpha" releases have stopped. This is known as the
"Beta" stage of the product. Several releases of the
product will be made during this time. Each release during
this phase is called a "Beta release".
A "Beta" release signifies that a "bug" has been eliminated
since the last "Beta" release.
Phase 5) Documentation
The user documentation is developed and written.
Phase 6) Release to public
Release to public is the final stage of the product. The
6
product is thought to be "bug free".
7
Version Numbering continued
---------------------------
Examples....
1.00.a1 First Alpha release of v1.00 (v1.00 will be a major
release)
1.00.a2 Second Alpha release of v1.00 (added some more
features)
1.00.a3 Third Alpha release of v1.00 (added some more features)
1.00.b1 First Beta release (stopped adding features, now
concentrating on finding bugs) e.g. Entering phase 4
1.00.b2 Second Beta release (fixed some bugs)
1.00.b3 Third Beta release (fixed some more bugs)
1.00 First Public release (a/k/a Major Release) No known
bugs!
1.01 Fixed some minor bug(s) that were not detected in Beta
Test stage (usually a spelling error, etc.)
1.10 Fixed some major bug(s) that were not detected in Beta
Test stage OR added some program functionality that
wasn't thought of at development time.
2.00.a1 First Alpha release of v2.00 (v2.00 will be a major
release) i.e. v2.00 starts back at phase 1 and is (for
all pratical purposes) a new product.
8
Syntax Conventions
------------------
This documentation uses the following syntax conventions:
... Ellipsis means something was omitted.
< > Metavariable: something you must furnish
<exp?> Expression of specific data-type where ? equals C
for character, D for date, N for numeric, M for
memo, L for logical or any type if omitted.
<memvar> Name of a memory variable
[] Optional syntax.
[...] Option may be repeated zero or more times.
| A choice: ON | OFF, Numeric | Date, etc.
Variable naming conventions
---------------------------
The following is a table of the variable naming conventions used
in all the examples and source code in my library.
Character Numeric Logical Date
+-------------------------------------------+
Local | c_name n_name l_name d_name |
Parameter | pc_name pn_name pl_name pd_name |
Local Array | ac_name an_name al_name ad_name |
Parameter Array | pac_name pan_name pal_name pad_name |
+-------------------------------------------+
Examples:
c_LastName is a name for a character variable contains a last
name.
n_Acct is a name for a numeric variable containing an account
number
gc_Color is a name for a Global (PUBLIC) character variable
containing a color setting.
9